home *** CD-ROM | disk | FTP | other *** search
- Path: engnews1.Eng.Sun.COM!taumet!clamage
- From: "john (j.d.) hickin" <hickin@bnr.ca>
- Newsgroups: comp.std.c++
- Subject: Re: auto_ptr again
- Date: 26 Jan 1996 22:56:56 GMT
- Organization: Bell-Northern Research
- Approved: clamage@eng.sun.com (comp.std.c++)
- Message-ID: <4ebhn5$lgt@bmtlh10.bnr.ca>
- NNTP-Posting-Host: taumet.eng.sun.com
- Mime-Version: 1.0
- Content-Type: text/plain; charset="us-ascii"
- Content-Transfer-Encoding: 7bit
- X-Nntp-Posting-Host: bmtlh520.bnr.ca
- X-Mailer: Mozilla 1.1 (X11; I; HP-UX A.09.05 9000/715)
- X-Url: news:3108FE66.FFD@suphys.physics.su.oz.au
- X-Lines: 16
- Content-Length: 787
- Originator: clamage@taumet
-
- |> For the record, I have no objections to token passing per se --
- |> it's just another storage management idiom. What I object to is the use
- |> of copy syntax for a non-copying operation, and the fact that this
- |> idiom is far less useful than reference counting, and not constrained
- |> enough for a Holder style class.
-
- And this, the expectation that constructors of the form X(X&) and X(const X&)
- must perform a *copy* operation, is, IMHO, the trouble. The original term was
- reference constructor, a name which, in my opinion, carefully stepped around
- all subtleties of language. Copy is a loaded term because the C++ meaning
- and the English langauge definition are not the same.
-
- --
- John Hickin Bell-Northern Research, Montreal, Quebec
- (514) 765-7924 hickin@bnr.ca
-
-
- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu.
- Contact address: std-c++-request@ncar.ucar.edu. The moderation policy
- is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
-
-